home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
JCSM Shareware Collection 1993 November
/
JCSM Shareware Collection - 1993-11.iso
/
cl040
/
qslot32.lzh
/
QSLOT.DOC
< prev
next >
Wrap
Text File
|
1993-03-01
|
15KB
|
317 lines
Q-Slot - Version 3.2
Copyright 1989-1993 by Motor City Software
All Rights Reserved
╒══════════════════════════════════════════════════════════════════════════╕
│░░░░░░ LICENSING INFORMATION ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ Q-Slot 3.2 ░░░│
╘══════════════════════════════════════════════════════════════════════════╛
Motor City doors are commercial programs marketed under the
"User Supported" or "Shareware" concept. You are allowed to
install this program on Your system and evaluate it before
deciding whether to purchase a license to continue using it. This
program is not public domain or freeware. If you use this program
for more than 30 days after successful installation, you are
legally required to register it or remove all working copies from
your system.
The User Supported or Shareware concept works only if you
and your fellow sysops support it. If you find this program
useful, you can register it for only $15.00 in U.S. funds. This
will help offset the development costs, and encourage us to write
other programs that might be useful to you. After all, no one
likes to work for nothing! A Registration Form is included in the
RATS distribution archive.
QSlot is Copyrighted 1990,91,92,93 by Motor City Software, ALL
RIGHTS RESERVED. You may copy this program and documentation for
backup purposes. You also may copy and share UNMODIFIED copies of
the original program archive. The copyright notice must remain
attached to all copies.
You may not sell Motor City Software products for a fee, or
distribute it along with other products without written permis-
sion of Motor City Software, nor may you modify or remove the
Copyright Notice from the program or the documentation. BBS
operators who charge for access to their systems are exempt from
this provision as long as no additional payment is required for
access to Motor City Software products beyond basic file access.
All Motor City Software products are extensively tested
before being publicly released, but as with any software, bugs
may still occur. Motor City Software products are provided as is,
and neither Motor City Software nor any BBS operator distributing
this software is responsible for any damage incurred during the
operation of this program. You are advised to test all Motor
City Software products thoroughly on a backup copy of your BBS
before putting them online.
Comments, suggestions and bug reports are welcome. If you
have any, you may call one of the Motor City Software Support
Systems listed in SUPPORT.DOC and leave a message to the Sysop.
If you're reporting a bug, please give as much detail as possible
about the problem you are having, your system configuration, and
if you would be willing to test possible corrections to the
problem.
╒══════════════════════════════════════════════════════════════════════════╕
│░░░░░░ INTRODUCTION ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ Q-Slot 3.2 ░░░│
╘══════════════════════════════════════════════════════════════════════════╛
Q-Slot! is an online ANSI graphics "Slot Machine" door game for QuickBBS
and RemoteAccess BBS.
It allows users to gamble their time remaining while online. The program
is pretty straight forward and and easy to install. It does require ANSI
graphics to be turned ON by the user and does require the DOS ANSI.SYS
driver to be installed on the host computer. If a caller tries to run
Q-Slot! and does not have graphics turned on, the program will notify the
user that graphics are required. It will then return control to the BBS.
Q-Slot! allows the BBS Sysop to define the maximum number of turns allowed
per user, per day as well as the maximum number of minutes a user may win
while in the game. Once a user has reached a maximum number of winable
minutes, the user is not allowed to access the game until the next day.
Once a user has reached the maximum number of turns per day Q-Slot! will
not allow the user to take any more turns.
╒══════════════════════════════════════════════════════════════════════════╕
│░░░░░░ INSTALLATION ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ Q-Slot 3.2 ░░░│
╘══════════════════════════════════════════════════════════════════════════╛
NOTE: If you were running an older release of QSlot, please note the
node number is now 2 digits, ie QSLOT01.CFG rather than QSLOT1.CFG
You also need to delete the first line of the config file, as QSLot now
reads the drop files from the current directory.
Q-Slot is easy to install. A type 7 menu entry may be used, as follows:
Optional Data : D:\BBS\DOORS\QSLOT\QSLOT.EXE /N*N
When executed, Q-Slot! will look for its configuration file QSLOT##.CFG
in the same directory that Q-Slot! is in. The ## is replaced by a 2 digit
node number. Q-Slot! reads the first 6 lines of the configuration file
and gets its operating parameters. Edit the QSLOT##.CFG file to suit your
needs. QSlot will read the ExitInfo.BBS and Dorinfo1.def file from the
current directory.
LEAVE NO BLANK LINES between lines 1 through 6.
The 7 lines represent the following parameters:
Line 1 - Time Bank Path
This is the path to your Time Banking utility directory. A trailing
backslash is appended if one is not already specified. This is
the path where Q-Slot! will write the file 'THEBANK.EXT' .
Line 2 - Coin Value
Coin_value is a number from 1 to 10. This tells Q-Slot!
the value of a coin in minutes. For example, if you enter
a value of 2, each coin will have a value of 2 minutes. I
have found that a value of 2 works well.
Line 3 - Maximum Winable Daily Minutes
Max_Mins is a number from 1 to 1000. This tells Q-Slot!
the maximum number of minutes a user can win while in the
program. If a user meets or exceeds this number, the user will
be congratulated and politely asked to try again tomorrow. The
user will not be allowed access to Q-Slot! until the next day.
NOTE: This number does not include the time the user already has.
If this was set to 100 and the user had 99 minutes when he
entered the program, he would be allowed to win 100 minutes.
Installation Continued
──────────────────────
Line 4 - Maximum Daily Turns
Max_turns is a number from 1 to 1000. This tells Q-Slot!
the maximum number of turns a player may take per day. If
this number is reached, the user will not be allowed to take
any more turns.
Line 5 - External Time Bank Support
Specifying a value of 1 on this line tells Q-Slot! that you
wish to use time bank support. What this means is that if a
player is in Q-Slot! and wins an amount of time that would
overlap a system event, Q-Slot! will create or append a file
called THEBANK.EXT. This file would then contain the user's
name and the number of minutes to automatically deposit into
the user's time bank account. If you don't have a TimeBank
that supports THEBANK.EXT then you might want to have a look
at Motor City Software's RATS V2.00 which is being released
at the same time as this program.
For example, if there is a system event in 60 minutes and the
player wins 80 minutes Q-Slot! will give the player 60 minutes
of winnings and automatically bank the rest (20 minutes).
Note: Q-Slot! will write to the THEBANK.EXT file using in the
path specified in QSLOT.CFG.
Line 6 - Slot Type
You may specify one of three selection on this line. Slot Type
specifies which slot format to use. Valid entries for this line
are:
PROMPT_USER - Q-Slot! asks user which slot type to use
CITY_SLOTS - Forces Q-Slot! to use City Slots format
TWENTY_ONE_BELL - Forces Q-Slot! to use 21 Bell format
Twenty-One Bell Format
This format is similar to that of the actual machine by the same
name. It is modified slightly to include the 3-Skull combination.
Each reel contains 21 spaces. The payoff percentage of this
format is lower than the default format (City Slots) but it is
very close to the real thing. The 3-Cherry combination does
not exist in this format.
City Slots Format
City Slots has a higher payoff percentage but also has better odds
of hitting a 3-Skull combination. The 3-Cherry combination is
allowed in this format.
╒══════════════════════════════════════════════════════════════════════════╕
│░░░░░░ SUPPORT FILES ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ Q-Slot 3.2 ░░░│
╘══════════════════════════════════════════════════════════════════════════╛
The Q-Slot! archive comes with a few files needed by the program.
You can run Q-Slot! from any directory .
The files that come with the archive are:
QSLOT.EXE This is the program
QSLOT01.CFG This is the configuration file for node 1
QSLOT.ANS This is the formatted graphic used
QSLOT.ASC This is the formatted non-graphic used
QSLOT.HLP This is a formatted help file
QSLOT.DOC This document
NOTE: Do not edit or change the contents of QSLOT.ANS ,QSLOT.ASC
or QSLOT.HLP. These files are formatted specifically for
the program.
In addition to these files, Q-Slot! also creates and maintains some
files it needs to operate. These are:
QSLOT.DTE Julian date file. Erase this file if
you need to reset the game that day.
QSLOT.USR List of users who have reached a daily
limit and are not allowed to play again
that day.
QSLOT.TRN This keeps track of the user turn counts
for the day.
QSLOT.LOG This is the player log. It is a circular
text file which tracks the last 15 players
and how they did.
THEBANK.EXT External time bank utility file. This
file is created and maintained by Q-Slot!
╒══════════════════════════════════════════════════════════════════════════╕
│░░░░░░ MORE ON TIME BANKING ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ Q-Slot 3.2 ░░░│
╘══════════════════════════════════════════════════════════════════════════╛
When The Bank is run and locates THEBANK.EXT, it will read it through to
the end of the file updating or adding user accounts as needed. The format
of THEBANK.EXT is: User Name:Time
For example, if JOHN DOE wins 80 minutes and Q-SLot deposits 20 minutes
into his account, the following line will be appended to THEBANK.EXT:
JOHN DOE:20
A user's name can appear in this file more than once. The Bank will
handle it properly. For more details, see The Bank 1.00 or later, or
RATS 1.01 or later.
╒══════════════════════════════════════════════════════════════════════════╕
│░░░░░░ OTHER STUFF ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
╘══════════════════════════════════════════════════════════════════════════╛
Q-Slot also allows the Sysop to plug his/her BBS by displaying a file
called QSLOT.TXT, if it exists. So, if there's a message you'd like to
display before Q-Slot draws it's screen, just create an ASCII text file
called QSLOT.TXT and put it in the same directory as Q-Slot and it will
be displayed.
Sysop function keys:
[ALT]-[C] : Chat with word wrap.
[ESC] to quit chat.
[ALT]-[H] : Hang up on user.
[ALT]-[J] : Jump to DOS.
[ALT]-[T] : Unconditionally return user to BBS.
Up Arrow : Increase users time by 2 minutes.
Down Arrow : Decrease users time by 2 minutes.
╒══════════════════════════════════════════════════════════════════════════╕
│░░░░░░ NOTES FROM THE AUTHOR ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ Q-Slot 3.2 ░░░│
╘══════════════════════════════════════════════════════════════════════════╛
Q-Slot has built in carrier detect and inactivity timer routines.
When tested on COM1 thru COM4, carrier detect and inactivity timers both
worked flawlessly.
That's as far in as I'm going to go technically with this program.
Once you load it up, you will see that it is self-explainatory. The online
help file will explain the commands available and the winning combinations
and their values. But there are a few limitations that I would like to
mention.
Q-Slot will not allow a user with less than 3 minutes access to the
program.
When a player enters the game, their time remaining is recorded. They
are issued coins based on their time remaining and the coin value specified
by the Sysop. The field "Your Time" reflects the amount of time available
for gambling purposes. It does not affect the time the player has within
the program. If a player has 10 minutes left when he enters the program, he
can play for 10 minutes regardless of how much time he wins. The reason
for this is if a system event is pending in 10 minutes and the user enters
the program, then the program must return the user to the BBS in time for
that event to run. If the user has won time, he can call back after the
system event has run and the time should still be available provided it
was not truncated by the BBS (this may be the case if no time banking
support is used).
As always, if you have any questions, comments, or problems with this
program, feel free to contact one of the support systems listed in
SUPPORT.DOC